InfoMagic Standards 1994 January/InfoMagic Standards - January 1994.iso/ccitt/1992/t/t433_6.asc

Text File | 1991-12-31 | 38KB | 1,965 lines

6.6.5  Transfer-interrupt

6.6.5.1Purpose

       The transfer-interrupt procedure is used by the requesting DTAM═PM to handle a less severe (than those handled
by the other error handling procedures) error situation during the transfer procedure, if at least one checkpoint was confirmed
during the transfer procedure.

6.6.5.2APDUs used

       No APDUs are used in this procedure.

6.6.5.3Transfer-interrupt procedure

6.6.5.3.1Transfer-interrupt procedure mapped onto presentation service (normal mode)

       This procedure is driven by the following events:

       a)   a requesting DTAM═PM problem;

       b)   a P═ACTIVITY═INTERRUPT indication primitive;

       c)   a P═ACTIVITY═INTERRUPT confirm primitive.

6.6.5.3.1.1Requesting DTAM═PM problem

6.6.5.3.1.1.1If the requesting DTAM═PM detects a less severe problem and at least one checkpoint was confirmed
during the transfer procedure, it issues a P═ACTIVITY═INTERRUPT request primitive with one of the following Reason
parameter values:

       a)   "non-specific error", if the problem was indicated by an exception reporting procedure,

       b)   "local SS-User error", if the problem is a local requesting DTAM-PM problem.

6.6.5.3.1.2P═ACTIVITY═INTERRUPT indication primitive

6.6.5.3.1.2.1If the responding DTAM═PM receives a P═ACTIVITY═INTERRUPT indication primitive, it issues:

       -    a P═ACTIVITY═INTERRUPT response primitive followed by a D═TRANSFER indication in Reliable transfer
            mode 1;

       -    a P═ACTIVITY═INTERRUPT response primitive in Reliable transfer mode 2.

6.6.5.3.1.3P═ACTIVITY═INTERRUPT confirm primitive

6.6.5.3.1.3.1If the requesting DTAM═PM receives a P═ACTIVITY═INTERRUPT confirm primitive, it issues:

       -    D═TRANSFER confirmation to the requesting DTAM user in Reliable transfer mode 1;

       -    the transfer-resumption procedure in Reliable transfer mode 2.

6.6.5.3.2Transfer-interrupt procedure mapped onto session service (transparent mode)

       This procedure is driven by the following events:

       a)   a requesting DTAM═PM problem:































1           Fascicle VII.7 - Rec. T.433





       b)   a S═ACTIVITY═INTERRUPT indication primitive;

       c)   a S═ACTIVITY═INTERRUPT confirm primitive.

6.6.5.3.2.1Requesting DTAM═PM problem

6.6.5.3.2.1.1If the requesting DTAM═PM detects a less severe problem and at least one checkpoint was confirmed
during the transfer procedure, it issues a S═ACTIVITY═INTERRUPT request primitive with one of the following Reason
parameter values:

       a)   "non-specific error", if the problem was indicated by an exception reporting procedure;

       b)   "local SS-User error", if the problem is a local requesting DTAM═PM problem.





















































                                                    Fascicle VII.7 - Rec. T.433      2


6.6.5.3.2.2S═ACTIVITY═INTERRUPT indication primitive

6.6.5.3.2.2.1If the responding DTAM═PM receives an S═ACTIVITY═INTERRUPT confirm primitive, it issues an
S═ACTIVITY═INTERRUPT response primitive followed by D═TRANSFER indication.

6.6.5.3.2.3S═ACTIVITY═INTERRUPT confirm primitive

6.6.5.3.2.3.1If the requesting DTAM═PM receives an S═ACTIVITY═INTERRUPT confirm primitive, it issues
D═TRANSFER confirmation to the requesting DTAM user.

6.6.6  Transfer-discard

6.6.6.1Purpose

       The transfer-discard procedure is used by the requesting DTAM═PM to escape from a more severe (than those
handled by the transfer-interrupt procedure) error situation, or a less severe error situation if no checkpoint was confirmed,
during the transfer procedure.

6.6.6.2APDUs used

       No APDUs are used in this procedure.

6.6.6.3Transfer-discard procedure

6.6.6.3.1Transfer-discard procedure mapped onto presentation service (normal mode)

       This procedure is driven by the following events:

       a)   a requesting DTAM═PM problem;

       b)   a P═ACTIVITY═DISCARD indication primitive;

       c)   a P═ACTIVITY═DISCARD confirm primitive.

6.6.6.3.1.1Requesting DTAM═PM problem

6.6.6.3.1.1.1If the requesting DTAM-PM detects a more severe problem, or a less severe problem if no checkpoint was
confirmed during the transfer procedure, it issues a P═ACTIVITY═DISCARD request primitive with one of the following reason
parameter values:

       a)   "non-specific error", if the problem was indicated by an error reporting procedure;

       b)   "local SS-User error", or "unrecoverable procedural error", if the problem is a local requesting DTAM═PM
            problem.

6.6.6.3.1.2P═ACTIVITY═DISCARD indication primitive

6.6.6.3.1.2.1If the responding DTAM═PM receives a P═ACTIVITY═DISCARD indication primitive, it issues:

       -    a P═ACTIVITY═DISCARD response primitive followed by D═TRANSFER indication in reliable transfer mode
            1;

       -    a P═ACTIVITY═DISCARD response primitive in reliable transfer mode 2.

6.6.6.3.1.2.2The responding DTAM═PM deletes all knowledge and contents of the associated DTAM user information
(segments of document information) so far received.

6.6.6.3.1.2.3If the responding DTAM═PM has already issued a D═TRANSFER indication primitive, it performs the
association-abort procedure. The abort-reason field of the DAB APDU is "transfer- completed".

6.6.6.3.1.3P═ACTIVITY═DISCARD confirm primitive

6.6.6.3.1.3.1If the requesting DTAM-PM receives a P═ACTIVITY═DISCARD confirm primitive, it issues:

       -    D═TRANSFER confirmation to the requesting DTAM user in reliable transfer mode 1;

       -    the transfer-retry procedure in reliable transfer mode 2.









3           Fascicle VII.7 - Rec. T.433




6.6.6.3.2Transfer-discard procedure mapped onto session service (transparent mode)

       This procedure is driven by the following events:

       a)   a requesting DTAM═PM problem;

       b)   an S═ACTIVITY═DISCARD indication primitive;

       c)   an S═ACTIVITY═DISCARD confirm primitive.

6.6.6.3.2.1Requesting DTAM═PM problem

6.6.6.3.2.1.1If the requesting DTAM-PM detects a more severe problem, or a less severe problem if no checkpoint was
confirmed during the transfer procedure, it issues an S═ACTIVITY═DISCARD request primitive with one of following reason
parameter values:

       a)   "non-specific error", if the problem was indicated by an error reporting procedure;

       b)   "local SS-User error", or "unrecoverable procedural error", if the problem is a local requesting DTAM-PM
            problem.

6.6.6.3.2.2S═ACTIVITY═DISCARD indication primitive

6.6.6.3.2.2.1If the responding DTAM-PM receives an S═ACTIVITY═DISCARD indication primitive, it issues an
S═ACTIVITY═DISCARD response primitive followed by D═TRANSFER indication in reliable transfer mode 1.

6.6.6.3.2.2.2The responding DTAM-PM deletes all knowledge and contents of the associated DTAM user information
(segments of document information) so far received.

6.6.6.3.2.2.3If the responding DTAM-PM has already issued a D═TRANSFER indication primitive, it performs the
session-abort procedure by issuing an S═U═ABORT request.

6.6.6.3.2.3S═ACTIVITY═DISCARD confirm primitive

       If the requesting DTAM-PM receives an S═ACTIVITY═DISCARD confirm primitive, it issues D═TRANSFER
confirmation to the requesting DTAM user in reliable transfer mode 1.

6.6.7  Transfer-resumption

6.6.7.1Purpose

       The transfer-resumption procedure is used in the reliable transfer mode 2 by the requesting DTAM═PM to recover
from:

       a)   an error situation handled by the transfer-interrupt procedure, or

       b)   an error situation handled by the association-abort procedure during a transfer procedure. In this case the
            transfer-resumption procedure is performed after an association- recovery procedure is successfully
            performed. If no checkpoint was confirmed in the interrupted transfer procedure, the transfer-discard
            procedure followed by the transfer-retry procedure are performed.

6.6.7.2APDUs used

       No APDUs are used in this procedure.

6.6.7.3Transfer-resumption procedure

6.6.7.3.1Transfer-resumption procedure mapped onto presentation service (normal mode)

       This procedure is driven by the following events:

       a)   the resumption of an interrupted activity;

       b)   a P═ACTIVITY═RESUME indication primitive.











                                                    Fascicle VII.7 - Rec. T.433      4


       After these events, the transfer procedure is used to continue (see  6.6.3).

6.6.7.3.1.1Resumption of an interrupted activity

6.6.7.3.1.1.1The requesting DTAM-PM issues a P═ACTIVITY═RESUME request primitive with parameters that link the
resumed activity to the previously interrupted one.
























































































































5           Fascicle VII.7 - Rec. T.433




6.6.7.3.1.1.2After the requesting DTAM═PM has issued the P═ACTIVITY═RESUME request primitive and at least one
checkpoint was confirmed in the interrupted transfer procedure, it continues the transfer procedure by issuing a P═DATA
request primitive for the segment of interchange-data-elements following the last confirmed checkpoint. If no checkpoint was
confirmed in the interrupted transfer procedure, the transfer-discard procedure followed by the transfer-retry procedure are
performed.

6.6.7.3.1.2P═ACTIVITY═RESUME indication primitive

6.6.7.3.1.2.1If the responding DTAM-PM receives a P═ACTIVITY═RESUME indication primitive, it checks the old activity
identifier and the old session connection identifier parameters of the P═ACTIVITY═RESUME indication primitive with the
corresponding information (session-connection-identifier and activity identifier) recorded for the last completely secured transfer
(see  6.6.3.1.4.3).

6.6.7.3.1.2.2If the information coincides with the recorded ones, the responding DTAM-PM either (a) responds correctly
to the requesting DTAM-PM according to the normal transfer procedure, but discards the data it receives, and does not issue
a D-TRANSFER indication primitive, or (b) performs the user-exception-report procedure with a Reason parameter value of
"sequence error".

6.6.7.3.1.2.3If the information does not coincide, the transfer-resumption procedure continues as for the transfer
procedure with a P-DATA indication primitive for the segment of interchange-data- element following the last confirmed
checkpoint.

6.6.7.3.1.2.4If the responding DTAM-PM cannot resume the activity, the responding DTAM-PM performs the user-
exception-report procedure.

6.6.8  Association-recovery

6.6.8.1Purpose

       The association-recovery procedure is used by the association-initiating DTAM-PM to recover from an error
situation handled by the association-abort procedure or the association-provider-abort procedure.

       This procedure is for further study.

6.7    Document unconfirmed manipulation

       Document unconfirmed manipulation is used by the requestor to manipulate the constituents of ODA and
operational structure which are commonly handled by both communication entities. Document unconfirmed manipulation
consists of document create operation, document delete operation, document modify operation, document call operation and
document rebuild operation.

6.7.1  Document create operation

6.7.1.1Purpose

       The document create operation procedure is used by the requestor of document manipulation to add the
constituents of ODA and operational structure to a document without any confirmation of the create manipulation.

6.7.1.2APDUs used

       The document create operation procedure uses D═CREATE (DCR) APDU.

6.7.1.2.1DCR APDU

       The field of the DCR APDU is listed in Table 10/T.433.


                                   TABLE 10/T.433

                                   DCR APDU field
w
                  ┌──────────────────┬────────┬────────┬──────────┐
                  │    Field name    │Presence│ Source │   Sink   │
                  ├──────────────────┼────────┼────────┼──────────┤
                  │Create information│   M    │  req   │   ind    │
                  └──────────────────┴────────┴────────┴──────────┘






                                                    Fascicle VII.7 - Rec. T.433      6


6.7.1.3   Document create operation procedure

6.7.1.3.1 Document create operation procedure mapped onto presentation service (normal
          mode)

     Procedure is driven by the following events:

     a)   a D═CREATE request primitive from the requestor;

     b)   a DCR APDU as user data of a P-DATA indication primitive.

6.7.1.3.1.1   D═CREATE request primitive

6.7.1.3.1.1.1 If the requesting DTAM-PM receives a D-CREATE request primitive, a  DCR
APDU is formed from the parameter  values  of  the  D═CREATE  request  primitive  and
transferred as user-data of a P═DATA request primitive. This may be done outside of an
activity.

6.7.1.3.1.2   DCR APDU

6.7.1.3.1.2.1 If the responding DTAM-PM receives the DCR APDU as user data of a P-DATA
indication primitive, the responding DTAM-PM issues a D-CREATE indication primitive to
the responder. The D═CREATE indication primitive parameter is derived from the DCR APDU.

6.7.1.4   Use of the DCR APDU fields

     The DCR APDU fields are used as specified below.

6.7.1.4.1 Create information

     This is the create information parameter value from the D-CREATE request primitive.
It appears as the create information  parameter  value  of  the  D-CREATE  indication
primitive.

6.7.2Document delete operation

6.7.2.1   Purpose

     The document delete operation procedure is used by  the  requestor  of  document
manipulation to delete the constituents of ODA and operational structure of an existing
document without any confirmation of the delete operation.

6.7.2.2   APDUs used

     The document delete operation procedure uses D═DELETE (DDL) APDU.

6.7.2.2.1 DDL APDU

     The field of the DDL APDU is listed in Table 11/T.433.



                                   TABLE 11/T.433

                                   DDL APDU field

w
           ┌─────────────────────┬────────┬────────┬──────────┐
           │      Field name     │Presence│ Source │   Sink   │
           ├─────────────────────┼────────┼────────┼──────────┤
           │Delete information   │   M    │  req   │   ind    │
           └─────────────────────┴────────┴────────┴──────────┘


6.7.2.3   Document delete operation procedure

6.7.2.3.1 Document delete operation procedure mapped onto presentation service (normal
          mode)



7           Fascicle VII.7 - Rec. T.433





     This procedure request is driven by the following events:

     a)   a D-DELETE request primitive from the requestor;

     b)   a DDL APDU as user data of P-DATA indication primitive.
























































































































                                                    Fascicle VII.7 - Rec. T.433      8


6.7.2.3.1.1   D═DELETE request primitive

6.7.2.3.1.1.1 If the requesting DTAM-PM receives a D-DELETE request primitive, a  DDL
APDU is formed from the parameter values of D-DELETE request primitive and transferred as
user-data of a P═DATA request primitive. This may be done outside of an activity.

6.7.2.3.1.2   DDL APDU

6.7.2.3.1.2.1 If the responding DTAM-PM receives the DDL APDU as user data of a P-DATA
indication primitive, the responding DTAM═PM issues a D-DELETE indication primitive to
the responder. The D═DELETE indication primitive parameter is derived from the DDL APDU.

6.7.2.4   Use of the DDL APDU fields

     The DDL APDU fields are used as specified below.

6.7.2.4.1 Delete information

     This is the delete information parameter value from the D-DELETE request primitive.
It appears as the delete information  parameter  value  of  the  D-DELETE  indication
primitive.

6.7.3Document modify operation

6.7.3.1   Purpose

     The document modify operation procedure is used by  the  requestor  of  document
manipulation to modify the attributes of constituents of ODA and operational structure of
an existing document without any confirmation of the modifying operation.

6.7.3.2   APDUs used

     The document modify operation procedure uses D-MODIFY (DMD) APDU.

6.7.3.2.1 DMD APDU

     The field of the DMD APDU is listed in Table 12/T.433.


                                   TABLE 12/T.433

                                   DMD APDU field

w
            ┌────────────────────┬────────┬────────┬──────────┐
            │      Field name    │Presence│ Source │   Sink   │
            ├────────────────────┼────────┼────────┼──────────┤
            │ Modify information │   M    │  req   │   ind    │
            └────────────────────┴────────┴────────┴──────────┘

6.7.3.3   Document modify operation procedure

6.7.3.3.1 Document modify operation procedure mapped onto presentation service (normal
          mode)

     This procedure is driven by the following events:

     a)   a D═MODIFY request primitive from the requestor;

     b)   a DMD APDU as user data of a P-DATA indication primitive.

6.7.3.3.1.1   D-MODIFY request primitive

6.7.3.3.1.1.1 If the requesting DTAM-PM receives a D-MODIFY request primitive, a  DMD
APDU is formed from the parameter values of D-MODIFY request primitive and transferred as
user-data of a P═DATA request primitive. This may be done outside of an activity.

6.7.3.3.1.2   DMD APDU




9           Fascicle VII.7 - Rec. T.433




6.7.3.3.1.2.1 If the responding DTAM-PM receives the DMD APDU as user data of a P-DATA
indication primitive, the responding DTAM-PM issues a D-MODIFY indication primitive to
the responder. The D═MODIFY indication primitive parameter is derived from the DMD APDU.




























































































































                                                    Fascicle VII.7 - Rec. T.433      10


6.7.3.4   Use of the DMD APDU fields

     The DMD APDU fields are used as specified below.

6.7.3.4.1 Modify information

     This is the modify information parameter value from the D-MODIFY request primitive.
It appears as the modify information  parameter  value  of  the  D-MODIFY  indication
primitive.

6.7.4Document call operation

6.7.4.1   Purpose

     The document call operation procedure is  used  by  the  requestor  of  document
manipulation to address or to read an object of operational structure which contains a
sequence of DTAM protocol data units (with some restrictions, i.e. that only D═CREATE,
D═DELETE and D═MODIFY can appear in this sequence). These  protocol  data  units  are
applicable to the existing document.

6.7.4.2   APDUs used

     The document call operation procedure uses D-CALL (DCL) APDU.

6.7.4.2.1 DCL APDU

     The field of the DCL APDU is listed in Table 13/T.433.


                                   TABLE 13/T.433

                                   DCL APDU field

w
            ┌────────────────────┬────────┬────────┬──────────┐
            │      Field name    │Presence│ Source │   Sink   │
            ├────────────────────┼────────┼────────┼──────────┤
            │ Call information   │   M    │  req   │   ind    │
            └────────────────────┴────────┴────────┴──────────┘


6.7.4.3   Document call operation procedure

6.7.4.3.1 Document call operation procedure mapped onto presentation service  (normal
          mode)

     This procedure is driven by the following events:

     a)   a D═CALL request primitive from the requestor;

     b)   a DCL APDU as user data of a P-DATA indication primitive.

6.7.4.3.1.1   D═CALL request primitive

6.7.4.3.1.1.1 If the requesting DTAM-PM receives a D-CALL request primitive, a DCL APDU
is formed from the parameter values of D-CALL request primitive and transferred as user-
data of a P═DATA request primitive. This may be done outside of an activity.

6.7.4.3.1.2   DCL APDU

6.7.4.3.1.2.1 If the responding DTAM-PM receives the DCL APDU as user data of a P-DATA
indication primitive, the responding DTAM-PM issues a D-CALL indication primitive to the
responder. The D-CALL indication primitive parameter is derived from the DCL APDU.

6.7.4.4   Use of the DCL APDU fields
















11           Fascicle VII.7 - Rec. T.433





     The DCL APDU fields are used as specified below.

6.7.4.4.1 Call information

     This is the call information parameter value from the D-CALL request primitive. It
appears as the call information parameter value of the D-CALL indication primitive.

6.7.5Document rebuild operation

     (For further study.)














































































































                                                    Fascicle VII.7 - Rec. T.433      12


6.8  Document confirmed manipulation

     (For further study.)

6.9  Typed data transfer

6.9.1Purpose

     Typed data transmission is used independent of the data token and is issued from
both DTAM users when required.

6.9.2APDUs usedw

     The typed data transfer procedure uses D-TYPED-DATA (DTD) APDU.

6.9.2.1   DTD APDU

     The field of the DTD APDU is listed in Table 14/T.433.


                                   TABLE 14/T.433

                                   DTD APDU field
w
       ┌──────────────────────────────┬────────┬────────┬──────────┐
       │           Field name         │Presence│ Source │   Sink   │
       ├──────────────────────────────┼────────┼────────┼──────────┤
       │ Typed data information       │   M    │  req   │   ind    │
       └──────────────────────────────┴────────┴────────┴──────────┘


6.9.3Typed data transfer procedure

6.9.3.1   Typed data transfer procedure mapped onto presentation service

     This procedure is driven by the following events:

     a)   a D═TYPED═DATA request primitive from the requestor;

     b)   a DTD APDU as user data of a P-TYPED-DATA indication primitive.

6.9.3.1.1 D-TYPED-DATA request primitive

6.9.3.1.1.1   If the requesting DTAM-PM receives a D-TYPED-DATA request primitive, a DTD
APDU is formed from the  parameter  values  of  D-TYPED-DATA  request  primitive  and
transferred as user-data of a P═TYPED═DATA request primitive.

6.9.3.1.2 DTD APDU

6.9.3.1.2.1   If the responding DTAM-PM receives the DTD APDU as user data of a P-TYPED-
DATA indication primitive, the responding DTAM═PM issues  a  D-TYPED-DATA  indication
primitive to the responder.  The D═TYPED═DATA indication primitive parameter is derived
from the DTD APDU.

6.9.4Use of the DTD APDU fields

     The DTD APDU fields are used as specified below.

6.9.4.1   Typed data information

     This is the typed data information parameter value from the D═TYPED═DATA request
primitive. It appears as the typed data information parameter value of the D═TYPED═DATA
indication primitive.

6.10 Remote document access

     (For further study.)



13           Fascicle VII.7 - Rec. T.433





6.11 Remote document management

     (For further study.)


























































































































                                                    Fascicle VII.7 - Rec. T.433      14


6.12 Token control

6.12.1    Token please control

6.12.1.1  Purpose

     The token please procedure is used by a requestor (receiver of documents) to request
the token from the responder (sender of documents).

6.12.1.2  APDUs used

     The token please procedure uses the D-TOKEN-PLEASE (DTP) APDU.

6.12.1.2.1DTP APDU

     The field of the DTP APDU is listed in Table 15/T.433.


                                   TABLE 15/T.433

                                   DTP APDU field

w
          ┌───────────────────────┬────────┬────────┬──────────┐
          │       Field name      │Presence│ Source │   Sink   │
          ├───────────────────────┼────────┼────────┼──────────┤
          │ Priority              │   U    │  req   │   ind    │
          └───────────────────────┴────────┴────────┴──────────┘


6.12.1.3  Token please procedure

6.12.1.3.1Token please procedure mapped onto presentation service (normal mode)

     This procedure is driven by the following events:

     a)   a D═TOKEN═PLEASE request primitive from the requestor; and

     b)   a DTP APDU as user data of a P═TOKEN═PLEASE indication primitive.

6.12.1.3.1.1  D═TOKEN═PLEASE request primitive

6.12.1.3.1.1.1If the requesting DTAM-PM does not possess the  token  and  receives  a
D═TOKEN═PLEASE request from the requestor, a DTP APDU is formed from the parameter value
of the D═TOKEN═PLEASE request primitive and transferred as user data of a P═TOKEN═PLEASE
request primitive. This may be done either inside or outside an activity.

6.12.1.3.1.2  DTP APDU

6.12.1.3.1.2.1If the responding DTAM-PM receives the DTP  APDU  as  user  data  of  a
P═TOKEN═PLEASE indication primitive, the responding DTAM-PM issues  a  D═TOKEN═PLEASE
indication primitive to the responder. The D═TOKEN═PLEASE indication primitive parameter
is derived from the DTP APDU.

6.12.1.3.2Token please procedure mapped onto session service (transparent mode)

     This procedure is driven by the following events:

     a)   a D═TOKEN═PLEASE requestor primitive from the requestor;

     b)   an S═TOKEN═PLEASE indication primitive.

6.12.1.3.2.1  D═TOKEN═PLEASE request primitive










15           Fascicle VII.7 - Rec. T.433




6.12.1.3.2.1.1If the requesting DTAM-PM does not possess the  token  and  receives  a
D═TOKEN═PLEASE request from the requestor, DTAM-PM issues  a  S═TOKEN═PLEASE  request
primitive. This may be done either inside or outside an activity.

6.12.1.3.2.2  Implicit DTP APDU

6.12.1.3.2.2.1If the responding DTAM-PM receives an S═TOKEN═PLEASE indication primitive
without any APDU on its user data, the responding  DTAM-PM  issues  a  D═TOKEN═PLEASE
indication primitive to the responder.

























































                                                    Fascicle VII.7 - Rec. T.433      16


6.12.1.4  Use of the DTP APDU fields

     The DTP APDU fields are use as specified below.

6.12.1.4.1Priority

     This parameter is the priority of the action, governed by the data token, that the
requestor of the D═TOKEN═PLEASE service wishes to carry out. This parameter has to be
supplied by the requestor of the D═TOKEN═PLEASE service.

6.12.2    Token give control

6.12.2.1  Purpose

6.12.2.1.1The token-give procedure is used by a requestor (sender of documents) to give
the token to the responder (receiver of documents).

6.12.2.1.2The requestor becomes the receiver and the responder becomes the sender.

6.12.2.2  APDUs used

     No APDUs are used in this procedure.

6.12.2.3  Token give procedure

6.12.2.3.1Token give procedure mapped onto presentation service (normal mode)

     This procedure is driven by the following events:

     a)   a D═TOKEN═GIVE request primitive;

     b)   a P═TOKEN═GIVE indication primitive.

6.12.2.3.1.1  D═TOKEN═GIVE request primitive

6.12.2.3.1.1.1If the requesting DTAM-PM possesses the token and receives a D═TOKEN═GIVE
request primitive from the requestor, it issues a P═TOKEN═GIVE request primitive  and
becomes the responding DTAM-PM. This may be done only outside an activity.

6.12.2.3.1.2  P═TOKEN═GIVE indication primitive

6.12.2.3.1.2.1If the responding DTAM-PM receives a P═TOKEN═GIVE indication primitive,
the responding DTAM═PM issues a D═TOKEN═GIVE indication primitive to the responder. The
responding DTAM═PM becomes the requesting DTAM═PM.

6.12.2.3.2Token give procedure mapped onto session service (transparent mode)

     This procedure is driven by the following events:


















































17           Fascicle VII.7 - Rec. T.433





     a)   a D-TOKEN-GIVE request primitive from the requestor;

     b)   an S═TOKEN═GIVE indication primitive.

6.12.2.3.2.1  D-TOKEN-GIVE request primitive

6.12.2.3.2.1.1If the requesting DTAM═PM possesses the token and receives a D═TOKEN═GIVE
request primitive from the requestor, it issues an S═TOKEN═GIVE request primitive and
becomes the responding DTAM═PM. This may be done only outside an activity.

6.12.2.3.2.2  S═TOKEN═GIVE indication primitive

6.12.2.3.2.2.1If the responding DTAM═PM receives an S═TOKEN═GIVE indication primitive,
the responding DTAM═PM issues a D═TOKEN═GIVE indication primitive to the responder. The
responding DTAM═PM becomes the requesting DTAM═PM.

6.12.3    Control-give

6.12.3.1  Purpose

6.12.3.1.1The CONTROL-GIVE procedure is used by a requestor to give all the tokens to
the responder.

6.12.3.1.2The requestor becomes the receiver and the responder becomes the sender.

6.12.3.2  APDUs used

     No APDUs are used in this procedure.









































                                                    Fascicle VII.7 - Rec. T.433      18


6.12.3.3  CONTROL-GIVE procedure

6.12.3.3.1CONTROL-GIVE procedure mapped onto presentation service (normal mode)

     This procedure is driven by the following events:

     a)   a D═CONTROL═GIVE request primitive;

     b)   a P═CONTROL═GIVE indication primitive.

6.12.3.3.1.1  D═CONTROL═GIVE request primitive

6.12.3.3.1.1.1If  the  requesting  DTAM═PM  possesses  the  tokens  and  receives   a
D═CONTROL═GIVE request primitive from the requestor, it issues a P═CONTROL═GIVE request
primitive and becomes the responding DTAM-PM. This may be done only outside an activity.

6.12.3.3.1.2  P═CONTROL═GIVE indication primitive

6.12.3.3.1.2.1If the responding DTAM═PM receives a P═CONTROL═GIVE indication primitive,
the responding DTAM-PM issues a D═CONTROL═GIVE indication primitive to the responder. The
responding DTAM═PM becomes the requesting DTAM-PM.

6.12.3.3.2CONTROL GIVE procedure mapped onto session service (transparent mode)

     This procedure is driven by the following events:

     a)   a D═CONTROL═GIVE request primitive from the requestor;

     b)   an S═CONTROL═GIVE indication primitive.

6.12.3.3.2.1  D═CONTROL═GIVE request primitive

6.12.3.3.2.1.1If  the  requesting  DTAM═PM  possesses  the  tokens  and  receives   a
D═CONTROL═GIVE request primitive from the requestor, it issues an S═CONTROL═GIVE request
primitive and becomes the responding DTAM═PM. This may be done only outside an activity.

6.12.3.3.2.2  S═CONTROL═GIVE indication primitive

6.12.3.3.2.2.1If the responding DTAM═PM receives an S═CONTROL═GIVE indication primitive,
the responding DTAM-PM issues a D═CONTROL═GIVE indication primitive to the responder. The
responding DTAM═PM becomes the requesting DTAM═PM.


6.13 Exception report

6.13.1    User-exception report

6.13.1.1  Purpose

     The user-exception-report procedure is used by the responding DTAM-PM to report an
error situation to the requesting DTAM-PM during document bulk transfer.

6.13.1.2  APDUs used

     No APDUs are used in this procedure.

6.13.1.3  User-exception report procedurew

6.13.1.3.1User-exception-report procedure mapped onto  presentation  service  (normal
          mode)

     This procedure is driven by the following events:

     a)   a responding DTAM-PM problem;

     b)   a P═U═EXCEPTION═REPORT indication primitive.

6.13.1.3.1.1  Receiving DTAM═PM problem






19           Fascicle VII.7 - Rec. T.433




6.13.1.3.1.1.1If  the  responding  DTAM═PM   detects   a   problem,   it   issues   a
P═U═EXCEPTION═REPORT request primitive. Depending on the severity of the detected error,
the value of the Reason parameter of the P═U═EXCEPTION═REPORT request primitive is as
follows:

     a)   in severe problem situations, the value "receiving ability jeopardized"  is
          used;



























































                                                    Fascicle VII.7 - Rec. T.433      20


     b)   in exceptional circumstances, the responding DTAM═PM may have to  delete  a
          partially  received  document   information,   even   though   some   minor
          synchronization points  have  been  confirmed.  In  this  case,  the  value
          "unrecoverable procedure error" is used;

     c)   if the responding DTAM═PM is not willing to complete a transfer procedure (see
           6.6.3), the value "non-specific error" is used;

     d)   if the requesting DTAM═PM resumes a transfer procedure already finished by the
          responding DTAM═PM within an application-association, the  value  "sequence
          error" is used;

     e)   for all other less severe error situations, the value "local SS-User error" is
          used.

6.13.1.3.1.2  P═U═EXCEPTION═REPORT indication primitive

6.13.1.3.1.2.1If the requesting DTAM═PM receives  a  P═U═EXCEPTION═REPORT  indication
primitive, it performs one of the following procedures depending on the Reason parameter
value of the P═U═EXCEPTION═REPORT indication primitive and Reliable transfer modes:

     a)   With a value "receiving ability jeopardized",

          -   the transfer-abort procedure (see  6.4.3.1.4)  followed  by  the  DTAM
              provider-abort procedure are performed (mode 1/2).

     b)   With a value "unrecoverable procedure error",

          -   the transfer-discard procedure (see   6.6.6)  followed  by  D-TRANSFER
              service (indication and confirmation) are performed (mode 1),

          -   the transfer-discard  procedure  followed  by  transfer  procedure  are
              performed (mode 2).

     c)   With a value "non-specific error",

          -   the transfer-discard procedure followed by D═TRANSFER service (indication
              and confirmation) are performed (mode 1),

          -   the transfer-discard  procedure  followed  by  transfer  procedure  are
              performed (mode 2).

     d)   With a value "sequence error",

          -   the transfer-discard procedure is performed and the requesting  DTAM═PM
              issues an D═TRANSFER confirm primitive with a  result  parameter  value
              "document-information- transferred" to the requestor and  the  transfer
              procedure is finished (mode 1/2).

     e)   With a value "local SS-User error" and at least one confirmed checkpoint in
          the transfer procedure,

          -   the transfer-interrupt procedure (see  6.6.5) followed  by  D═TRANSFER
              service (indication and confirmation) are performed (mode 1),

          -   the transfer-interrupt procedure followed  by  the  transfer-resumption
              procedure (see  6.6.7) are performed (mode 2).

     f)   With a value "local SS-User error" and no checkpoint was confirmed  in  the
          transfer procedure,

          -   the transfer-discard procedure followed by D═TRANSFER service (indication
              and confirmation) are performed (mode 1),



21           Fascicle VII.7 - Rec. T.433





          -   the transfer-discard procedure followed by the transfer  procedure  are
              performed (mode 2).

6.13.1.3.1.2.2Table 16/T.433 summarizes the actions of the  requesting  DTAM-PM  when
receiving the P═U═EXCEPTION═REPORT indication primitive.




























































                                                    Fascicle VII.7 - Rec. T.433      22